Software design sharing systems and methods

ABSTRACT

A system, method and software product shares a software design. A design sharer having machine readable instructions stored within memory of a development server and executable by a processor of the development server interacts with a first user to select a first portion of a first hierarchical software design. The design sharer saves the first portion within a public workspace. The design sharer interacts with a second user having access to the public workspace to select the first portion and inserts the first portion into a second hierarchical software design.

RELATED APPLICATIONS

This application claims priority to U.S. patent application Ser. No.61/835,254, titled “Software Design Sharing Systems and Methods,” filedJun. 14, 2013, and incorporated herein by reference.

BACKGROUND

Although there are models for code sharing (open source, commercialsubroutine libraries, etc.), there is currently nosoftware-design-sharing model. Software-design templates like thosedefined by IEEE Standard 1016-1998 simply allow for the translationbetween a software design and code. Software-design patterns do notrepresent a full design; that is, they are only meant to show high-levelsoftware-design best practices, execution strategies (task breakout) orprogram structure, not design to the level where code is to occur.

SUMMARY OF THE INVENTION

The MPT Hierarchical Design model defines work from the most abstractlevel down to where code occurs. All data flows, control-flow displays,data-storage looping structures, data-transformation processes, andcontrol processes are defined. The design is converted to asingle-process form, removing the design details, while keeping thedesign functionality. Removing the visible details has no effect on theMPT design-to-code-sharing association model (see U.S. patent pendingUS20120066664 for a full description); thus, the design may stillfunction as a design even though the details are hidden. Hiding designdetails protects the intellectual property that is the design. Thismeans that, like MPT shared code, it is possible to share designelements without the sharer losing his or her intellectual property.This document describes the MPT Hierarchical Design model, how toconvert hierarchical design elements into reusable elements, and thereusable design-element sharing process. The ability to merge sub-graphinformation into a process is also discussed. This is important as beingable to merge and un-merge sub-graphs allows the developer to controlthe performance as well as the flexibility of the system.

In one embodiment, a method shares a software design. A design sharerhaving machine readable instructions stored within memory of adevelopment server and executable by a processor of the developmentserver, interacts with a first user to select a first portion of a firsthierarchical software design. The design sharer saves the first portionwithin a public workspace. The design sharer interacts with a seconduser having access to the public workspace to select the first portionand inserts the first portion into a second hierarchical softwaredesign.

In another embodiment, a software design sharing system includes aprocessor, a memory, a conceptual public workspace that is representedwithin the memory for storing a first portion of a first hierarchicalsoftware design, a conceptual organization workspace that is representedwithin the memory for storing a remaining portion of the firsthierarchical software design, and a design sharer. The design sharer hascomputer readable instructions stored in the memory that when executedby the processor are capable of: interacting with a first user to selectthe first portion for storing within the public workspace; interactingwith a second user having access to the public workspace to select thefirst portion; and inserting the first portion into a secondhierarchical software design.

In another embodiment, a software product has instructions, stored onnon-transitory computer-readable media, wherein the instructions, whenexecuted by a computer, perform steps for software design sharing. Thesoftware product includes instructions for interacting with a first userto select a first portion of a first hierarchical software design;instructions for saving the first portion within a public workspace;instructions for interacting with a second user having access to thepublic workspace to select the first portion; and instructions forinserting the first portion into a second hierarchical software design.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram illustrating one exemplary software designsharing system, in an embodiment.

FIG. 2 shows one exemplary hierarchical decomposition graph,illustrating three decomposition levels.

FIG. 3 shows a context level, also known as Level 0, which representsthe entire software design of FIG. 1 as a single process (“process 0”).

FIG. 4 shows one exemplary screen shot illustrating the context level 0,of FIG. 3, as displayed by the development server of FIG. 1.

FIG. 5 shows a first decomposition level of context level, of FIG. 3,showing “process 0” decomposed into two internal processes that arecouples with multiple data-storage areas.

FIG. 6 shows one exemplary screen shot of the first decomposition levelof FIG. 5 generated within a sub-graph interaction screen by developmentserver and displayed on development computer.

FIG. 7 shows one exemplary process options selection list that isdisplayed when a designer, using the development computer, of FIG. 1,for example, right-clicks on the context level 0 of FIG. 3.

FIG. 8 shows one exemplary save process screen 800 that is displayedwhen save process button of FIG. 7 is selected.

FIG. 9 is a table showing exemplary process entries in the organizationworkspace of FIG. 1.

FIG. 10 is a table showing exemplary process entries in the publicworkspace of FIG. 1.

FIG. 11 shows one exemplary list of categories that is displayed when aselect category button, of FIG. 8, is selected by the developer.

FIG. 12 shows one exemplary new category entry screen that is displayedby the development server when the developer selects a create categorybutton of the save process screen of FIG. 8.

FIG. 13 shows one exemplary process information request screen that isdisplayed when a developer double clicks a row within the table of FIG.9, or the table of FIG. 10.

FIG. 14 shows one exemplary process description display screen that isdisplayed when the developer selects process description display buttonof FIG. 13.

FIG. 15 shows one exemplary input display screen that is displayed whenthe developer selects input description display button of FIG. 13.

FIG. 16 shows one exemplary keyword list screen that is displayed whenthe developer selects keyword list display button of FIG. 13.

FIG. 17 shows one exemplary test procedure display screen, showing testprocedures for the process, that is displayed when the developer selectstest procedure display button of FIG. 13.

FIG. 18 shows pull-down dragged onto sub-graph interaction screen ofFIG. 6 and displayed as a process.

FIG. 19 shows one exemplary graph object list that is displayed when thedeveloper selects “Pass Data” option from the option list of FIG. 7.

FIG. 20 shows one exemplary global view of software design of FIG. 1 inthe form of a hierarchical decomposition graph.

FIG. 21 shows one exemplary decomposition level view that providesdetails of one decomposition level of software design of FIG. 1.

FIG. 22 shows one exemplary decomposed-process view that providesdetails of one particular sub-graph of software design of FIG. 1.

FIG. 23 shows one exemplary screenshot illustrating a page view screenincluding one or more portions of one particular sub-graph of softwaredesign of FIG. 1.

FIG. 24 depicts an exemplary conversion view of a conversion ofdecomposition level of FIG. 5, into a finite state machine.

FIG. 25 shows a conversion view converting finite state machine of FIG.24 into optimized finite state machine.

FIG. 26 shows an exemplary optimized finite state machine with outerloop.

FIG. 27 shows an exemplary finite state machine with unassociatedprocesses.

FIG. 28 shows an exemplary lowest level sub-graph.

FIG. 29 shows an exemplary finite state machine based upon the sub-graphof FIG. 28.

FIG. 30 shows an exemplary finite state machine for merged processes.

FIG. 31 shows a screenshot including pull-down menu of sub-graphinteraction screen of FIG. 6 having a merge option button.

FIG. 32 shows a screenshot of the sub-graph interaction screen of FIG. 6including a merged symbol.

FIG. 33 shows a screenshot of the sub-graph interaction screen of FIG. 6including a processes option list.

FIG. 34 depicts a global view of software design of FIG. 1 includingselectable merge button on the bottom most level.

FIG. 35 depicts the global view of FIG. 34 with selectable merger buttonon the second bottom most level.

FIG. 36 depicts the global view of FIG. 34 with selectable merger buttonon the third bottom most level.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Hierarchical Design Model

FIG. 1 is a block diagram illustrating one exemplary software designsharing system 100. System 100 includes a development server 101 that islocated, for example, within cloud 160. Cloud 160 represents a computercommunication network that may include the Internet and other computernetworking technologies.

Development server 101 has a processor 106 and a memory 102 for storinga software design 110. Software design 110 is based upon a massivelyparallel hierarchical design model that defines work from the mostabstract level down to where code occurs. One or more developers eachuse a developer computer 150 that has a developer interface 156,including a display 152 and an input device 154, to communicate withdevelopment server 101 to develop software design 110. For example,developers may develop software design 110 within an organizationworkspace 120 that is shared between the multiple developers working fora particular organization, wherein developers working for otherorganizations do not have access to a non-sharable design portion 117 ofsoftware design 110 stored within organization workspace 120. Memory 102also stores a design sharer 108 that has machine readable instructionsthat are executed by processor 106 to share at least part of softwaredesign 110 as sharable design portion 116 within a public workspace 122.Public workspace 122 is for example accessible by developers other thanthose with access to organization workspace 120.

FIG. 2 shows one exemplary hierarchical decomposition graph 200 thatrepresents software design 110 of FIG. 1. Each decomposition levelcontains one or more sub-graphs 202, one sub-graph for each decomposingprocess. Each sub-graph 202 may be considered a code snippet in theMcCabe sense. Note that a process that decomposes into a singlelower-level process is invalid as no additional graph information isadded. A process may decompose into a sub-graph with a minimum of twoprocesses on it.

Software design 110, as represented by hierarchical decomposition graph200 of FIG. 2, may also be drawn using decomposition levels to hide theoverall complexity of software design 110 while retaining McCabe'scode-snippet concept. FIGS. 3, 5 and 6 show exemplary graphs thatrepresent software design 110, including a context level 300, and threedecomposition levels of sub-graphs 202.

FIG. 3 shows a context level 300, also known as Level 0, whichrepresents the entire software design 110 as a single process (“process0”).

FIG. 4 shows one exemplary screen shot 400 illustrating context level300 as displayed by development server 101 via one or more ofdevelopment computers 150, wherein process 402 represents “process 0” ofcontext level 300.

FIG. 5 shows a first decomposition level 500 of context level 300 ofFIG. 3, showing “process 0” decomposed into two internal processes 502and 504 that are couples with multiple data-storage areas 506(1)-(3).

FIG. 6 shows one exemplary screen shot 600 of first decomposition level500 of FIG. 5 generated within a sub-graph interaction screen 604 bydevelopment server 101 and displayed on development computer 150. Notethat context level 300 contains first decomposition level 500.

FIG. 7 shows one exemplary process options selection list 700 that isdisplayed when a designer, using development computer 150 for example,right-clicks on context-level process 402 (“Process 0”). One option inprocess options selection list 700 is a save process button 702. FIG. 8shows one exemplary save process screen 800 that is displayed when saveprocess button 702 is selected. A developer selects save process button702 to save the current process, along with its input/output data flows,description, keyword list, associated test procedures, and associatedcode, for future recall.

To save a process, the workspace is first selected. There are twopossible workspaces (places to store a process): organization workspace120 and public workspace 122. Where the developer selects a save processorganization workspace button 802 of save process screen 800, theprocess and its contents are stored as non-sharable design portion 117within organization workspace 120 and is accessible only to members(e.g., developers) of the creating organization. All entries inorganization workspace 120 are grouped by category name and processname. FIG. 9 is a table 900 showing exemplary organization workspaceprocess entries.

Where the developer selects a save process public workspace button 804of save process screen 800, the process and its contents are stored assharable design portion 116 within public workspace 122 and anyorganization (e.g., developer) may access the process. All entries inpublic workspace 122 are grouped by organization name, category, andprocess name. In public workspace 122, only the top-most level of theprocess is visible and none of the information associated with theprocess may be changed. FIG. 10 is a table 1000 showing exemplary publicworkspace process entries.

Once the workspace for storing the process is selected, the developernext selects either an existing category or a new category for theprocess. Categories are groupings of “like” processes. For example, an“Image Processing” category may be used to store FFT, Convolution, andedge-detection processes.

FIG. 11 shows one exemplary list 1100 of categories that is displayedwhen a select category button 806 is selected by the developer.Selection of one category from list 1100 causes the current process tobe stored under that category.

FIG. 12 shows one exemplary new category entry screen 1200 that isdisplayed by development server 101 when the developer selects a createcategory button 808 of save process screen 800. Using screen 1200,development server 101 requests a unique category name from thedeveloper, and then stores the current process under that category.

Only an authorized member of an organization using system 100 may saveor delete a process or category created by that organization. This istrue for adding or deleting a process or category in both organizationworkspace 120 and public workspace 122. Deleting either a category orprocess is analogous to creating one, with the only difference being theselection of the delete organization process button 812, delete publicprocess button 814, delete organization category button 816, and deletepublic category button 818 of save process screen 800, FIG. 8.

Using Saved Processes

To use a saved process, the “Use Existing Design Process” pull-down 602is selected, as shown in FIG. 6, which causes system 100 to display theorganization and public options. Selecting the organization optioncauses table 900 of FIG. 9 to display the organization workspace processentries. Selection of a row within table 900 allows that process to bedragged and dropped onto sub-graph interaction screen 604. Where thedeveloper selects the public option from pull-down 602, table 1000 ofFIG. 10 is displayed to show public workspace entries. Selecting a rowof table 1000 allows that process to be dragged and dropped ontosub-graph interaction screen 604.

FIG. 13 shows one exemplary process information request screen 1300 thatis displayed when a developer double clicks a row within table 900, FIG.9, or table 1000, FIG. 10. Each listed process within screen 1300 has aprocess description display button 1302, an input description displaybutton 1304, an output description display button 1306, a keyword listdisplay button 1308, and a test procedure display button 1310.

Selecting the Process Description Display button 1302 causes the“process description” display to be shown.

FIG. 14 shows one exemplary process description display screen 1400 thatis displayed when the developer selects process description displaybutton 1302. FIG. 15 shows one exemplary input display screen 1500 thatis displayed when the developer selects input description display button1304. Note: “Name” is the name of a variable, description is a textdescription of the variable, “Dim” is the number of dimensionsassociated with a variable, “Ind” is the number of indirections(pointers) needed to access the variable, “Type” is the data type of thevariable, and “Dim Size” is the maximum index size for each dimension ofthe variable. A similar screen is displayed for output information whenthe developer selects output description display button 1306. FIG. 16shows one exemplary keyword list screen 1600 that is displayed when thedeveloper selects keyword list display button 1308. FIG. 17 shows oneexemplary test procedure display screen 1700, showing test proceduresfor the process, that is displayed when the developer selects testprocedure display button 1310. Note: Parameter Name is the name of thevariable, Type is the type of the variable (integer, real, string,etc.), Dim is the dimensionality of the variable, File Name is the nameof a file containing the values that go into a multi-dimensionalvariable, and Value is the value put into a zero-dimensional variable.

Connecting a Saved Process to the Graph

As indicated above, a saved process is dragged and dropped ontosub-graph interaction screen 604 of FIG. 6. FIG. 18 is a screen shot1800 showing pull-down 602 dragged onto sub-graph interaction screen 604and displayed as process 1802. This action automatically displaysworkspace selection buttons 1804, and, in turn, table 900 of FIG. 9,wherefrom the saved process is selected. As input and output data flowsare connected to process 1802, the variables are automatically usedwithout changing the definitions provided when the process was saved.

Right-clicking on the saved process within table 900 (or on sub-graphinteraction screen 604) displays options list 700, FIG. 7, for theprocess. FIG. 19 shows one exemplary graph object list 1900 that isdisplayed when the developer selects “Pass Data” option 704 from optionlist 700. List 1900 defines valid graph objects to which to process 1802may connect. Selecting any one of the listed graph objects displays apopup 1902 that allows the developer to name the data flow. Thevariables displayed in popup 1902 define the variables that aretransferred via that dataflow (either input or output). The names,descriptions, DIMs, IND, type, and DIM size of the variables cannot bechanged.

Different Graph Views

Because of the hierarchical nature of the MPT Hierarchical DecompositionGraph (e.g. graph 200 of FIG. 2), three graphical views are possible:the global view, the level view, and the decomposed-process view.

Global View

FIG. 20 shows one exemplary global view 2000 of software design 110 ofFIG. 1 in the form of a hierarchical decomposition graph. Global view2000 shows all decomposition levels of software design 110 together.Global view 2000 graphically shows the following: the relationshipsamong different levels of process elements, the location ofdevelopers/administrators, developer access or privilege information,level-based test completeness (T0, T1, T2, T3), and level-basedwork-completeness percentage. The test completeness is defined asfollows: T0=at least one process on the associated decomposition levellacks a test procedure, T1=every process on the associated decompositionlevel has at least one test procedure, T2=every control-flow conditionattached to every process has at least one test procedure, and T3=everycontrol-flow condition attached to every process has at least one testprocedure for the minimum, maximum and nominal dataset values that mayoccur for that control-flow condition. A control-flow condition defineswhich data values and prior compute states allow access to the currentprocess.

To access a particular decomposition level from global view 2000, thedeveloper selects the appropriate “Level-x” button 2002. In the exampleof FIG. 20, “User-x” represents the name of a developer that has atleast “view” privileges at the associated level. “Administrator” is alabel associated with a user identified as an administrator, and“Developer” is a label associated with a user identified as a developer.A user whose name is written in green has edit privileges while a userwhose name is written in orange has view-only privileges.

Level View

FIG. 21 shows one exemplary decomposition level view 2100 that providesdetails of one decomposition level of software design 110 of FIG. 1. Allof the same information displayed for the entire graph in global view2000 of FIG. 20 is displayed for each decomposition level. Doubleleft-clicking on a sub-graph on the current level causes the DecomposedProcess View to be displayed. Since level view 2100 shows the details ofone particular decomposition level, the “Level” button 2002 is notshown. Selecting a Global button 2102 returns to display global view2000.

Decomposed Process View

FIG. 22 shows one exemplary decomposed-process view 2200 that providesdetails of one particular sub-graph of software design 110 of FIG. 1.All of the same information shown for a level is shown for a sub-graph.Double left-clicking on the sub-graph causes “sub-graph interaction”screen 604 of FIG. 6 to be displayed. From “Sub-graph Interaction”screen 604, selection of a “Decomp” button 606 causes system 100 toreturn to decomposed-process view 2200, selection of a Level button 2202causes system 100 to return to level view 2100, and selection of Globalbutton 2204 causes system 100 to return to global view 2000.

Sub-Graph Interaction Screen

FIG. 23 shows one exemplary screenshot 2300 illustrating a page viewscreen 2302 including one or more portions of one particular sub-graphof software design 110 of FIG. 1. The “sub-graph interaction” screen 604is the primary working area for graph manipulation. Page view screen2302 may be displayed concurrently, or on top of sub-graph interactionscreen 604 such that the sub-graph may be easily navigated. Page viewscreen 2302 is composed of multiple “pages” 2304. Each page 2304 shows aportion of the same sub-graph (i.e., to ensure that the complexity ofany part of the sub-graph is manageable). To access a particular page2304 of the current sub-graph, the user double-clicks the desired page.

Graph Execution Optimization

FIG. 24 depicts an exemplary conversion view 2400 of a conversion ofdecomposition level 500, of FIG. 5, into a finite state machine 2402.Because an MPT Hierarchical Decomposition Graph is executable (i.e. theprocesses are accessed from the control flows), serial-code performanceis important. The MPT Hierarchical Decomposition Graph is converted intoa finite state machine which is then executed. As an example,decomposition level 500, of FIG. 5, generates the finite state machine2402. Within finite state machine 2402, control 2404 (i.e. control 508)provides the sequencing of the processes. There is a performance problemwhen every process returns back to control 2404, potentially doublingthe number of transitions per process; the following is an example:

Finite state machine 2402 operates as follows. The control process iscalled via the “init” condition on its external input control flow. Thecontrol process calls “process.1” using the “init” condition.

When “process.1” is complete, it calls the control 2404 with a “return”condition. The “return” condition provides information on thetransitioning process; in this case the transitioning process is“process.1”.

Control 2404 calls “process.2” using the “After Process.1” condition.When “process.2” is complete, it calls the control process using a“return” condition.

Control 2404 exits after receiving the “return” condition from“Process.2”.

The processing performance may be increased if the finite state machine2402 recognizes sequencing, changing the finite state machine to thefinite state machine as illustrated in FIG. 25.

FIG. 25 shows a conversion view 2500 converting finite state machine2402 into optimized finite state machine 2502. Optimized finite statemachine 2502 gives the following transitions:

“Process.1” is called via the “init” condition on its external controlflow.

“Process.1” calls “process.2” using a “After Process.1” condition

“Process.2” exits using its “After Process.2” condition.

The optimized finite state machine 2502 has only three transitionscompared to the six transitions of the original finite state machine2402. There are two conditions which require the control process: a loopacross associated processes and managing multiple unassociatedprocesses.

If the containing process has a loop and the processes of the currentfinite state machine are associated then the control process is requiredto manage the looping indexes. This would change the optimized finitestate machine 2502 to the optimized finite state machine with outer loop2600 as illustrated in FIG. 26

If the processes of the MPT finite state machine 2402 are unassociatedthen the control process is used to correctly identify which process isto be accessed. This changes the optimized finite state machine 2502 tothe optimized finite state machine with unassociated processes 2700, asillustrated in FIG. 27:

Within the optimized finite state machine with unassociated processes2700, associated processes are linked together via sequencing; that is,every associated process in a particular finite state machine (otherthan the control process and the first non-control process) has an“after” clause as part of every one of its calling state transitions.Unassociated processes do not have an “after” clause in their callingstate transitions.

Merged Levels

MPT's Finite State Machine Execution model represents a new and uniqueform of computer language. In computer science, there are three generaltypes of languages: Assembly, Compiled, and Interpreted.

-   -   1) Assembly languages—a computer language that is translated        into machine-readable form. This translation is analogous to        compiling if it is translated into micro-code (not all machines        use micro-code).    -   2) Compiled languages—a computer language that is translated        into either byte code for interpretation or machine code for        direct machine execution.    -   3) Interpreted languages—a computer language that is indirectly,        via an interpreting computer program, executed.

Assembly code is typically the fastest computer code; however, moderncompilers have greatly narrowed the performance gap. The difficulty inwriting assembly code typically far outweighs the performance gainsobtained. Most modern computer programs are written in compiled orinterpreted languages. Compiled languages have far greater executionperformance than interpreted languages; however, they are less flexible.In an interpreted language, time-to-solution may be decreased becausethe compilation step is missing, shortening the design-code-compile-testcycle to a design-code-test cycle. Thus, quick solutions are typicallycreated using interpreted languages whereas production solutions aretypically compiled (if performance is an issue). There are some “mixed”languages, such as LISP, which may freely mix compiled and interpretedcode. However, mixed languages may not automatically transform compiledcode into interpreted code and back.

Consider that the MPT Hierarchical Decomposition Graph is translatedinto an executable finite state machine, e.g. as illustrated in FIGS.24-27. Further, consider that the states at the non-sub-graph processlevel represent compiled code and the state transitions representinterpreted code. The lowest sub-graph level contains only non-sub-graphprocesses (processes that do not decompose), by definition. Note asub-graph is a decomposed process.

FIG. 28 shows an exemplary lowest level sub-graph 2800. In FIG. 28,processes 2802(1), 2802(2), and 2802(3) are non-sub-graph processes asthey do not decompose further. Processes 2802 are all contained withinsub-graph 2800. Non-sub-graph processes contain only assignment andvariable-definition statements, not control statements.

Sub-graph 2800 may provide the following assignment statements:

C2.1 C2.2 C2.3 B = 1 B = A + C A = (A + B + C)/2 C = 2 A = A * 2 A = B +C

FIG. 29 shows an exemplary finite state machine 2900 based uponsub-graph 2800 of FIG. 28. Rather than containing separate internalprocesses 2802, finite state machine 2900 may contain the merger ofprocesses 2802(1), 2802(2), and 2802(3). The control flows, indicated bydashed lines, shown in FIG. 29 convert to “if” statements and with the“afterxxx” statements added as flags give the following code:

  C2 (int *A, int *B, int *C)  {  init = 1;  int AfterC2_1 = 0;  intAfterC2_2 = 0;  int AfterC2_3 = 0;  If (init)    {    *B=1;   *C=2;   *A=*B+*C;    AfterC2_1 = 1;    }  If (AfterC2_1 && *A>10)    {   *B=*A+*C;    *A=*A*2;    AfterC2_2 = 1;    }  If (AfterC2_2 ||(AfterC2_1)    {    *A=(*A+*B+*C)/2;    }  }

Merging the internal processes changes the finite state machine to afinite state machine for merged processes 3000 as illustrated in FIG.30.

FIG. 31 shows a screenshot 3100 including pull-down menu 3102 ofsub-graph interaction screen 604 having a merge option button 3104. Ingeneral, any group of processes at the same decomposition level may bemerged. The advantages of merger are: faster processing and the abilityto hide underlying functionality (giving Intellectual Propertyprotection). To merge processes, the user first accesses theto-be-merged decomposition level and selects the “Merge” button from the“Options” pull-down menu 3102:

FIG. 32 shows screenshot 3200 of sub-graph interaction screen 604including a merged symbol 3202. Mergers cannot take place unless thereis code associated with all to-be-merged non-control processes. Thismeans that only non-decomposable processes and merged processes may bemerged on a sub-graph. If there is a decomposable process on thesub-graph then an error message is displayed and merger does not occur.The merged sub-graph is grayed out on the screen to show that it is notaccessible. The process that decomposes into the merged sub-graph ischanged to contain the merged symbol (M) 3202.

Once a decomposable process is merged, it may switch from merged tounmerged use. Selecting the “M” merged symbol 3202 causes the symbol tochange to “U” for unmerged, and the decomposition level is accessible,modifiable, and executable. Selecting the “U” symbol causes thesub-graph to be re-merged. If there is a non-decomposable process on theto-be merged sub-graph then an error is displayed.

FIG. 33 shows screenshot 3300 of sub-graph interaction screen 604including a processes option list 3302. Another way to merge a processis to right-click on the decomposable process (i.e. process 3304), whichdisplays the “processes option list” 3302, then select the “Merge”option button 3306. Similarly, unmerging may be accomplished byright-clicking on the decomposable process followed by the selection ofthe “Unmerge” option button 3308. Since merging increases how much ofthe code is compiled to binary and un-merging increases how much of thecode is compiled, this means that compiled versus interpreted actssimply as different views of the same code rather than different statesof the code.

Group Merge

FIG. 34 depicts a global view 3400 of software design 110 includingselectable merge button 3402 on the bottom most level 3404. Merging andun-merging code does not have to be performed at the singleprocess/sub-graph level. Consider that at the bottom-most level 3404 ofthe graph no process decomposes. This means that it is possible to startat the bottom-most graph level and merge/un-merge all of decomposedprocesses on that level. Activating “Merge/Un-merge” button 3402 on thebottom-most level 3404 allows the developer to safely perform a groupmerge/un-merge. Once a level has been merged, then the next level up maybe merged. This process may be continued indefinitely.

FIG. 35 depicts global view 3400 of FIG. 34 with selectable mergerbutton 3502 on the second bottom most level 3406. At first only thebottom-most “Merge” button 3402 is active. Selecting the active mergebutton 3402 cause the sub-graph to be merged. Merger is depicted by thesub-graphs on the bottom most level 3404 being grayed out. The bottommost merge button 3402 then changes to un-merge and the second bottommost merge button 3502 on the next level up is activated.

FIG. 36 depicts global view 3400 of FIG. 34 with selectable mergerbutton 3602 on the third bottom most level 3408. Selecting the nextactive merge button 3502 causes level 3406 to be grayed out (and merged)and the merge button changes 3502 to un-merge while the bottom mostlevel button 3402 is grayed out and the merge button 3602 on the thirdfrom bottom most level 3408 is activated.

Conclusion

This document has described the MPT Hierarchical Design model, how toconvert hierarchical design elements into reusable elements, and areusable design-element sharing process. The ability to merge sub-graphinformation into a process was also discussed.

Changes may be made in the above methods and systems without departingfrom the scope hereof. It should thus be noted that the matter containedin the above description or shown in the accompanying drawings should beinterpreted as illustrative and not in a limiting sense. The followingclaims are intended to cover all generic and specific features describedherein, as well as all statements of the scope of the present method andsystem, which, as a matter of language, might be said to falltherebetween.

What is claimed is:
 1. A method for software design sharing, comprising:receiving an interaction, using a design sharer having machine readableinstructions stored within memory of a development server and executableby a processor of the development server, from a first user to select afirst portion of a first hierarchical software design, the firsthierarchical software design comprising a plurality of decompositionlevels containing one or more sub-graphs each representing a decomposingprocess; saving, using the design sharer, the first portion within apublic workspace; converting the first portion to a single-process formby removing design details while keeping design functionality of thefirst portion so that the top most level of the first portion is visibleand none of the information associated with the top most level ischangeable by a second user; receiving a second interaction, using thedesign sharer, from the second user having access to the publicworkspace to select the first portion; and inserting the first portioninto a second hierarchical software design, the second hierarchicalsoftware design comprising a plurality of decomposition levelscontaining one or more sub-graphs each representing a decomposingprocess; wherein the public workspace is accessible, via the designsharer, by any user and wherein the organization workspace isaccessible, via the design sharer, only by authorized users of anorganization associated with the organization workspace.
 2. The methodof claim 1, further comprising saving, using the design sharer, theremaining portion of the first hierarchical design within anorganization workspace.
 3. The method of claim 1, wherein the firstportion comprises a first process and associated process information ofthe first hierarchical software design.
 4. The method of claim 3,wherein the process information includes information chosen from thegroup including input/output data flows, description, keyword list,associated test procedures, associated code, and combinations thereof.5. The method of claim 3, the step of receiving a second interactionfrom the second user comprising: displaying an interactive visualrepresentation of the second hierarchical software design; selecting,via the design sharer, a second process within the second hierarchicalsoftware design; and selecting, via the design sharer, the first processto be used as the second process.
 6. A software design sharing system,comprising: a processor; a memory; a conceptual public workspace that isrepresented within the memory for storing a first portion of a firsthierarchical software design, the first hierarchical software designcomprising a plurality of decomposition levels containing one or moresub-graphs each representing a decomposing process, the public workspacebeing accessible by all users, and the organization workspace beingaccessible by only authorized users of an organization associated withthe organization workspace; a conceptual organization workspace that isrepresented within the memory for storing a remaining portion of thefirst hierarchical software design; a design sharer comprising computerreadable instructions stored in the memory that when executed by theprocessor are capable of: receiving a first interaction from a firstuser to select the first portion for storing within the publicworkspace; converting the first portion to a single-process form byremoving design details while keeping design functionality of the firstportion so that the top most level of the first portion is visible andnone of the information associated with the top most level is changeableby a second user; receiving a second interaction from a second userhaving access to the public workspace to select the first portion; andinserting the first portion into the second hierarchical softwaredesign, the second hierarchical software design comprising a pluralityof decomposition levels containing one or more sub-graphs eachrepresenting a decomposing process.
 7. The software design system ofclaim 6, the first portion comprising a first process and associatedprocess information.
 8. The software design system of claim 7, the firstsoftware design comprising at least one hierarchical decomposition leveleach having at least two first processes, wherein the design sharer iscapable of saving at least one of the first processes into the publicworkspace as the first portion.
 9. The software design system of claim7, wherein the process information is chosen from the group includinginput/output data flows, description, keyword list, associated testprocedures, associated code, and combinations thereof.
 10. The softwaredesign system of claim 7, wherein the design sharer is capable of:generating and displaying, on a display, an interactive visualrepresentation of the second hierarchical software design; interactingwith the second user to select, using an input device associated withthe display, a second process within the second hierarchical softwaredesign; and interacting with the second user to select the one firstprocess to be used as the second process.
 11. A software productcomprising instructions, stored on non-transitory computer-readablemedia, wherein the instructions, when executed by a computer, performsteps for software design sharing, comprising: instructions forinteracting with a first user to select a first portion of a firsthierarchical software design, the first hierarchical software designcomprising a plurality of decomposition levels containing one or moresub-graphs each representing a decomposing process; instructions forsaving the first portion within a public workspace, wherein the publicworkspace is accessible by any user and wherein the organizationworkspace is accessible only by authorized users of an organizationassociated with the organization workspace; instructions for convertingthe first portion to a single-process form by removing design detailswhile keeping design functionality of the first portion so that the topmost level of the first portion is visible and none of the informationassociated with the top most level is changeable by a second user;instructions for interacting with the second user having access to thepublic workspace to select the first portion; and instructions forinserting the first portion into a second hierarchical software design,the second hierarchical software design comprising a plurality ofdecomposition levels containing one or more sub-graphs each representinga decomposing process.
 12. The software product of claim 11, furthercomprising instructions for saving the remaining portion of the firsthierarchical design within an organization workspace.
 13. The softwareproduct of claim 11, wherein the first portion comprises a first processand associated process information of the first hierarchical softwaredesign.
 14. The software product of claim 13, wherein the processinformation includes information chosen from the group includinginput/output data flows, description, keyword list, associated testprocedures, associated code, and combinations thereof.
 15. The softwareproduct of claim 13, the instructions for interacting with the seconduser comprising: instructions for displaying an interactive visualrepresentation of the second hierarchical software design; instructionsfor selecting a second process within the second hierarchical softwaredesign; and instructions for selecting the first process to be used asthe second process.